Roadside assistance service provider assignment system

ABSTRACT

Aspects of the disclosure provide a computer-implemented method and system for the assignment of roadside assistance service providers such as tow trucks to distressed vehicles/drivers requiring roadside assistance. The methods and systems may include a roadside assistance service provider system with a collection module, an assignment module, and a feedback module. The collection module collects roadside assistance service provider information and historical statistics from real-world information and stores the information in a database that may then be analyzed using particular rules and formulas. The assignment module assigns particular roadside assistance service providers to particular distressed vehicles/drivers based on one or more characteristics. The feedback module may provide near real-time cues to the tow truck driver&#39;s mobile device, such as alerting when the amount of time spent on a task exceeds a predefined threshold, flagging high priority tasks/assignments, providing a step-by-step checklist for the repair.

This application is a continuation of U.S. application Ser. No. 15/010,545; filed Jan. 29, 2016 which is a continuation of U.S. application Ser. No. 14/798,138, filed Jul. 13, 2015 which claims priority to Provisional Application, U.S. Ser. No. 62/030,966, filed Jul. 30, 2014, which is incorporated herein by reference in its entirety.

FIELD OF THE INVENTION

The disclosure relates generally to methods and systems for mobile or online service providers. More specifically, the disclosure provides computer-implemented methods and systems that relates to the assignment of a roadside assistance service provider to distressed vehicles/drivers requiring roadside assistance.

BACKGROUND

Services provided to users, such as roadside assistance services, automobile services, home services, and other personal services, are traditionally serviced through professional service providers that can be expensive and difficult to schedule. Specifically, roadside assistance service providers provide towing services, flat tire assistance, fuel services, automobile repairs, oil changes, and scheduled maintenance appointments, etc. Most prior art systems might auto assign roadside assistance service providers or tow truck drivers solely based on the proximity to a distressed vehicle. Telematics devices are known and used in the art to provide various telematics information to users and/or service providers regarding their location, direction of travel, velocity, route, and/or destination. Additionally, there is a vast wealth of insurance information that includes locations and instances for previous accidents, previous insurance claims, and driving history.

Accordingly, it would be desirable to provide roadside assistance service provider systems and methods for safe and effective service requests and assigning using a system that takes a sophisticated approach to collecting various types of data through sensors and systems, analyzes that data, and assigns roadside assistance service providers based on a complex plurality of factors/characteristics for a more optimized assignment. It would be desirable to include telematics information and service provider information to locate the service providers based on the location of the services requested and to prioritize the service providers based on the user preferences, telematics information, additional factors, and insurance information of the service providers

BRIEF SUMMARY

The following presents a simplified summary of the invention in order to provide a basic understanding of some aspects of the disclosure. This summary is not an extensive overview of the invention. It is not intended to identify key or critical elements of the invention or to delineate the scope of the invention. The following summary merely presents some concepts of the invention in a simplified form as a prelude to the more detailed description provided below.

A first aspect of the disclosure provides a computer-implemented method for a roadside assistance service provider system. The method may comprise: (1) receiving, through a roadside assistance service provider application executing on a roadside assistance service provider server having at least one processor, a roadside assistance service request from a driver of a distressed vehicle; (2) collecting, by a plurality of sensors in communication with a vehicle of a roadside assistance service provider, roadside assistance service provider information; (3) collecting, by the roadside assistance server provider server, historical statistics data based on real-world roadside assistance services; (4) receiving, by the roadside assistance service provider server, telematics information from a telematics device; (5) comparing, by the roadside assistance service provider server, the roadside assistance service request with the roadside assistance service provider information, the telematics information, and the historical statistics data to determine a timeline and a distance for each individual roadside assistance service provider; (6) providing, by the roadside assistance service provider server, a prioritized ranking of roadside assistance service providers based on the roadside assistance service provider information, the telematics information, the historical statistics data, and the roadside assistance service request; (7) providing, by the roadside assistance service provider server, an assignment for roadside assistance services to the highest ranked roadside assistance service provider from the comparison and prioritized ranking steps; and (8) providing, by the roadside assistance service provider server, roadside assistance event notifications for the roadside assistance services.

Another aspect of the disclosure provides a computer-implemented method for a roadside assistance service provider system. The method may comprise: (1) receiving, through a roadside assistance service provider application executing on a roadside assistance service provider server having at least one processor, a roadside assistance service request from a driver of a distressed vehicle, wherein the roadside assistance service request includes one or more of the following: jump start the distressed vehicle, flat tire change, tow automobile, or locked out of vehicle; (2) collecting, by a plurality of sensors in communication with a vehicle with a roadside assistance driver, roadside assistance driver information; (3) collecting, by the roadside assistance server provider server, historical statistics data based on real-world roadside assistance services; (4) receiving, by the roadside assistance service provider server, telematics information from a telematics device; (5) comparing, by the roadside assistance service provider server, the roadside assistance service request with the roadside assistance driver information, the telematics information, and the historical statistics data to determine a timeline and a distance for each individual roadside assistance driver; (6) providing, by the roadside assistance service provider server, a prioritized ranking of roadside assistance drivers based on the roadside assistance driver information, the telematics information, the historical statistics data, and the roadside assistance service request; (7) providing, by the roadside assistance service provider server, an assignment for roadside assistance services to the highest ranked roadside assistance driver from the comparison and prioritized ranking steps; (8) providing, by the roadside assistance service provider server, a reassignment of the roadside assistance service request, wherein the reassignment includes shuffling the assignments during an assignment process; (9) providing, by the roadside assistance service provider server, roadside assistance event notifications for the roadside assistance services; and (10) providing, by the roadside assistance service provider server, a reward if the roadside assistance driver meets particular times for the roadside assistance service request.

In another aspect of the disclosure, one or more non-transitory computer readable media storing computer readable instructions that, when executed, may cause an apparatus to: (a) receive, through a roadside assistance service provider application executing on a roadside assistance service provider server having at least one processor, a roadside assistance service request from a driver of a distressed vehicle; (b) collect roadside assistance service provider information by a plurality of sensors in communication with a vehicle of a roadside assistance service provider; (c) collect, by the roadside assistance server provider server, historical statistics data based on real-world roadside assistance services; (d) determine, by the roadside assistance service provider server, an amount of time for each task within the roadside assistance service provider request necessary for a given roadside assistance service provider; (e) receive, by the roadside assistance service provider server, telematics information from a telematics device; (f) compare, by the roadside assistance service provider server, the roadside assistance service request with the roadside assistance service provider information, the telematics information, and the historical statistics data to determine a timeline and a distance for each individual roadside assistance service provider; (g) provide, by the roadside assistance service provider server, a prioritized ranking of roadside assistance service providers based on the roadside assistance service provider information, the telematics information, the historical statistics data, and the roadside assistance service request; (h) provide, by the roadside assistance service provider server, an assignment for roadside assistance services to the highest ranked roadside assistance service provider from the comparison and prioritized ranking steps; and (i) provide, by the roadside assistance service provider server, roadside assistance event notifications for the roadside assistance services, wherein the event notification is on a display to the roadside assistance service provider, and further wherein the display provides a reminder to the roadside assistance service provider when the roadside assistance service provider has gone beyond an average time for each of the tasks.

The details of these and other embodiments of the present disclosure are set forth in the accompanying drawings and the description below. Other features and advantages of the disclosure will be apparent form the description and drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the present invention and the advantages thereof may be acquired by referring to the following description in consideration of the accompanying drawings, in which like reference numbers indicate like features, and wherein:

FIG. 1 is an illustrative network environment and computing systems that may be used to implement aspects of the present disclosure;

FIG. 2 is an illustrative example operating environment that may be used to implement the processes and functions of certain aspects of the present disclosure;

FIG. 3A illustrates an exemplary flow diagram of a mobile service provider system and application that may be used to implement various aspects of the disclosure; and

FIG. 3B illustrates an exemplary block diagram of a mobile service provider system and application that may be used to implement various aspects of the disclosure; and

FIG. 4 illustrates a method of providing a mobile service provider system and application in accordance with aspects of the disclosure; and

FIG. 5 illustrates another method of providing a mobile service provider system and application that includes insurance aspects in accordance with aspects of the disclosure.

FIG. 6 illustrates an exemplary block diagram of a roadside assistance service provider system that may be used to implement various aspects of the disclosure; and

FIG. 7 illustrates a method of providing a roadside assistance service provider system in accordance with aspects of the disclosure; and

FIG. 8 illustrates another method of providing a roadside assistance service provider system in accordance with aspects of the disclosure.

DETAILED DESCRIPTION

In the following description of the various embodiments, reference is made to the accompanying drawings, which form a part hereof, and in which is shown by way of illustration various embodiments in which the subject matter of the disclosure may be practiced. It is to be understood that other embodiments may be utilized and structural and functional modifications may be made without departing from the scope of the present disclosure.

Aspects of the disclosure provide a computer-implemented method and system for individuals to be non-professional service providers. The methods and systems may include the use of an application on a mobile device that provides telematics information, service provider information to locate the service providers; prioritizes the service providers based on the user preferences, telematics information, and service provider information; and facilitates the service provider request and the electronic payment for the services. A system may allow the individual to register as a service provider and include their skills and qualifications. The system may provide a performance rating and/or user comments for the service providers. When a user needs services, such as a tire repair, the system may notify the service providers that meet predetermined criteria and allows them to bid on the services. The system may then select a service provider or allows the user to select the service provider. The system can include roadside services, automobile services, home services, and personal services. Telematics information regarding the user and/or the vehicle may be utilized to provide information regarding the service provider's location, velocity (instantaneous and average), route, and destination. The computer-implemented method and system may utilize insurance information to provide additional features and to enhance the mobile service provider methods and systems by providing known and safe routes and recommendations to the user as described and detailed below.

Additional aspects of the disclosure may also provide a computer-implemented method and system for non-professional individuals, e.g. freelancers to provide services such as automobile repair, etc. to third parties (users). The computer-implemented method and system may allow individuals to register as service providers. The individuals may identify their qualifications, the types of services they can perform and their location. The computer-implemented method and system may determine a safety rating of the service provider based on various parameters such as a driving score, car insurance information, and payment history, etc. The computer-implemented method and system may determine a performance rating of the service provider based on various user ratings and comments. The computer-implemented method and system may be utilized on a computer, laptop, internet, or mobile devices. The computer-implemented method and system may also track the individual's location through telematics information so that when a user needs services, a list of potential service providers may be displayed to the user based on the user's location and other factors. The service providers may also be informed about the services required and the price through a push notification. The service providers may then also elect to provide the service at a set price.

FIG. 1 illustrates a block diagram of a mobile service provider server or a roadside assistance service provider server 101 (e.g., a computer server) in communication with a mobile service provider system 100 that may be used according to an illustrative embodiment of the disclosure. A roadside assistance service provider system 600 as illustrated in FIG. 6 may also be represented by reference number 100 in FIG. 1. The mobile service provider server or roadside assistance service provider server 101 may have a processor 103 for controlling overall operation of the a mobile service provider server or roadside assistance service provider server 101 and its associated components, including RAM 105, ROM 107, input/output component 109, and memory 115.

Input/Output (I/O) 109 may include a microphone, keypad, touch screen, and/or stylus through which a user of the a mobile service provider server or roadside assistance service provider server 101 may provide input, and may also include one or more of a speaker for providing audio output and a video display device for providing textual, audiovisual and/or graphical output. Additionally, a hands-free or voice aspect may be utilized to provide input for the mobile service provider server or roadside assistance service provider server 101. Software may be stored within memory 115 and/or storage to provide instructions to processor 103 for enabling the mobile service provider server or roadside assistance service provider server 101 to perform various functions. For example, the memory 115 may store software used by the mobile service provider server or roadside assistance service provider server 101, such as an operating system 117, application programs 119, and an associated database 121. The processor 103 and its associated components may allow the mobile service provider server or roadside assistance service provider server 101 to run a series of computer-readable instructions to receive service requests from a user, receive telematics information, and analyze this information to provide a prioritized ranking of service providers to fulfill the service request. Additionally, the processor 103 and its associated components may allow the mobile service provider server or roadside assistance service provider server 101 to provide service provider information, and transmit a selected service provider to a user or service provider. Additionally, the processor 103 and its associated components may allow the mobile service provider server or roadside assistance service provider server 101 to run a series of computer-readable instructions to provide an electronic payment for the service provided, receive confirmation of the order, and provide rewards to the user. In addition, the processor 103 may receive insurance information in order to enhance and improve the service providing process. Further still, the processor 103 may derive insurance rating factors for insurance coverage and premiums based on the service provider, specific service request, and the frequency of the service requests.

The mobile service provider server or roadside assistance service provider server 101 may operate in a networked environment supporting connections to one or more remote computers, such as terminals 141 and 151. The terminals 141 and 151 may be personal computers or servers that include many or all of the elements described above relative to the mobile service provider server or roadside assistance service provider server 101. Alternatively, terminal 141 and/or 151 may be data stores for storing information related to service provider and user information or insurance information. The network connections depicted in FIG. 1 include a local area network (LAN) 125 and a wide area network (WAN) 129 but may also include other networks. When used in a LAN networking environment, the mobile service provider server or roadside assistance service provider server 101 is connected to the LAN 125 through a network interface or adapter 123. When used in a WAN networking environment, the mobile service provider server or roadside assistance service provider server 101 may include a modem 127 or other means for establishing communications over the WAN 129, such as the Internet 131. It will be appreciated that the network connections shown are illustrative and other means of establishing a communications link between the computers may be used. The existence of any of various well-known protocols such as TCP/IP, Ethernet, FTP, HTTP and the like is presumed.

Additionally, an application program 119 used by the mobile service provider server or roadside assistance service provider server 101 according to an illustrative embodiment of the disclosure may include computer executable instructions for invoking functionality related to mobile service provider and insurance systems. The application program 119 may be detailed further as the mobile service provider application 300. The mobile service provider server 101 and/or terminals 141 or 151 may also be mobile terminals including various other components, such as a battery, speaker, and antennas (not shown).

The disclosure is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with the disclosure include, but are not limited to, personal computers, server computers, hand-held or laptop devices, mobile devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, and distributed computing environments that include any of the above systems or devices, and the like.

The disclosure may be described in the general context of computer-executable instructions, such as program applications or modules, being executed by a computer. Generally, program applications or modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The disclosure may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, the program applications or modules may be located in both local and remote computer storage media including memory storage devices.

FIG. 2 illustrates an example system including various components for facilitating a mobile service provider application and mobile service provider process. The application system 200 may include an application development environment 205, an application store or repository 210, a user mobile device 215, and a mobile service provider system 100. The application development environment 205 may be operated by an insurance provider such as an insurance company. Application development environment 205 may include a hardware environment or a software environment. For example, the application development environment 205 may be provided on a server. Alternatively or additionally, the application development environment 205 may be provided as a software environment in which applications may be constructed and tested. The application development environment 205 may further be used to validate the integrity of applications before deployment through one or more distribution channels such as application store/repository 210. Validating the integrity of an application may include executing the application against multiple data sets to insure correct operation, verifying security and privacy protections, verifying that the application adheres to one or more requirements or regulations (e.g., industry requirements, government regulations, privacy guidelines/requirements) and the like and/or combinations thereof.

Once the application has been published to the application store/repository 210, the application may be made available to a general public, subscribers to the application store/repository 210, or users of a particular operating system, service or other environment. Example application stores or repositories may include the APPLE App Store, the Android Market, the Microsoft Store, the Blackberry App World, and/or any other similar application stores or repositories. The application may be downloaded to one or more devices through the application store/repository 210. In some arrangements, downloading of the applications may be restricted to particular operating systems, hardware devices, device capabilities, software requirements and the like and/or combinations thereof.

The user mobile device 215 may be configured to execute applications provided through the application store/repository 210. For example, user mobile device 215 may execute a mobile service provider application 300 to help a user provide a service request safely and quickly from their vehicle. User mobile device 215 and the application executing thereon may communicate with a mobile service provider system 100.

Application development environment 205, application store or repository 210 and mobile service provider system 100 may correspond to a single device, system, server, or location. In other arrangements, the application development environment 205, application store or repository 210 and mobile service provider system 100 may be provided as a distributed system among multiple locations and/or devices. The user mobile device 215 may be located remotely from one or more of application development environment 205, application store/repository 210 and/or mobile service provider system 100. The various devices and systems 205, 210, 215 and 100 of the application system 200 may communicate with one another using various protocols and through various networks. For example, the user mobile device 215 may transmit and receive data through a cellular network or other types of wireless networks (e.g., Wi-Fi or Bluetooth or other known and used wireless methods known and used in the art). Alternatively or additionally, communications may be facilitated using a hand-free service with the user mobile device 215. Alternatively or additionally, communications may be facilitated using wired connections and protocols.

The present disclosure may utilize an in-vehicle device 225 to collect and provide telematics information as known and used in the art. The in-vehicle device 225 may include a processor with a display or graphical interface that receives and/or collects driving data and/or telematics information and provides additional information based on the driving data. The driving data and/or telematics information may include, but not be limited to: location, instantaneous velocity, average velocity, route, destination, etc. The in-vehicle device 225, which may be configured to receive real-time vehicle data, may provide a driver with visual and/or audible in-vehicle information. The in-vehicle device 225 may process real-time (i.e., near real-time) data and then display the processed information in a meaningful way on a display or graphical user interface (GUI). The in-vehicle device 225 may receive and/or collect critical driving data and store summary information for and/or about the driver.

The in-vehicle device 225 may communicate with a data collection device or on-board diagnostics port of a vehicle to collect the driving data. In another exemplary embodiment, the in-vehicle device 225 may acquire the driving data directly from the device, such as a smart phone, tablet computer, or vehicle navigation system via a built-in accelerometer and/or a Global Positioning System (GPS).

FIG. 3A illustrates an exemplary flow diagram of a mobile service provider system 100 and application that may be used to implement various aspects of the disclosure. Generally, the mobile service provider system 100 may utilize different phases, such as a registration phase 160, a need phase 165, a payment phase 170, and a reporting phase 180. The mobile service provider system 100 may include each of the four different phases. The system is a continuous process as illustrated by the circular flow of from each of the four different phases.

During the registration phase, a mobile service provider application 300 may be available to a new user. The user may download this mobile service provider application 300 on to a mobile device. Alternatively, the user may utilize the mobile service provider application 300 via the internet on an internet form or a website. The potential user may then complete a user profile and enter their information, such as name, address, phone number, services potentially needed. The potential user may also be able to register using the insurance information which includes all of the pertinent and required information. After the user completes their user profile, the user may then be asked if the user wants to be a service provider also. The user profile and/or the service provider profile may then be saved to the mobile service provider system 100. During the registration phase, a potential service provider may also register. The potential service provider may be complete service provider profile and enter their information, such as name, address, phone number, services provided, and any other qualifications necessary or linked to the services. The potential service provider may also be able to register using the insurance information which includes all of the pertinent and required information. The potential service provider may then be qualified, validate, or verified. The service provider system 100 may qualify, validate, or verify the service provider using the insurance information as described and provided by the insurance server, such as safe driver information or current payment information. This qualification, validation, and/or verification may provide a pre-screening tool for the users to ensure a quality and safe service provider. The service provider profile may then be saved to the mobile service provider system 100. The user and/or the service provide may allow the system to know or track their locations at all times to help facilitate the matching of users and service providers. Additionally, the insurance information and/or telematics information may allow the mobile service provider system 100 to tie the location to the users and the service providers through the telematics device or mobile device.

During the need phase, a user may submit a service request in the mobile service provider system 100. The mobile service provider system 100 may then filter potential service providers based on the nature of the service request, location of service providers, and other criteria based on providers. The mobile service provider system 100 may then determine any possible business or user goals associated with the service request, such as customer happiness, lowest cost, and timeliness. Based on the business goals, the mobile service provider system 100 may then further filter the potential service providers. The mobile service provider system 100 may detect whether a person who has accepted the service request will fulfill the service request. Based on this acceptance or non-acceptance, the mobile service provider system 100 may then resubmit the service request and/or cancel the previous service request. The mobile service provider system 100 may then provide the user with information about the service provider, such as credit risk, insurance information, driving score, premium risk, evaluation information, telematics information. The mobile service provider system 100 may also provide the user with information regarding the status of the services, i.e. service confirmation, start time, service provider en-route, service provider onsite, service completed, and/or service canceled.

During the payment phase, the user may provide the payment for the services rendered. The mobile service provider system 100 may be configured to allow for and provide an electronic payment for the services rendered. The mobile service provider system 100 may be configured to allow for the electronic payment to be automatic with a pre-entered payment method, such as credit card information, bank information, PayPal, google wallet, etc. With the automatic electronic payment method, the mobile service provider system 100 will automatically send the payment information to the mobile service provider system 100 after an order has been placed. Additionally, the mobile service provider system 100 may be configured to allow for manual individual input of payment methods with each service provider. In the manual electronic payment method, a service request may not be complete until the user manually inputs payment information to pay for the services. Additionally, the mobile service provider system 100 may be configured to provide a yearly membership for the services, whereas the customer does not pay for each individual service request. Additionally, the service provider may receive a non-monetary benefit for providing the services.

During the reporting phase, the mobile service provider system 100 may provide reporting and tracking capabilities. The mobile service provider system 100 may provide both real-time dashboard reporting as well as historical reporting. The real-time dashboard may include a service provider view and a service view. The service provider view may include and show the following: how many active service providers at any given point in time, where the service providers are located, and/or what the service providers are doing. The service view may include and show the following: how many active service requests at any given point in time, what the current status of active service requests, was the service level agreement (SLA) met or not. The historical reporting may include reporting of the service requests, which may include monthly/daily totals, types of service requests, region-wise reporting, met SLA or not, etc. The historical reporting may also include the reporting of “up-sell” numbers, such as the number of service requests, the service types, and the dollar amounts associated with those service requests.

FIG. 3B is an example block diagram of a mobile service provider system 100 and mobile service provider application 300. The mobile service provider application 300 may include a variety of software or firmware modules such as one or more of the following: a user module 305, service provider module 310, a telematics module 315, a reward module 320, an insurance module 325, an electronic payment module 330, and an evaluation module 335. Each of these modules may be utilized by the mobile service provider application 300.

The user module 305 may be configured to do one or more of the following: provide registration services, request services, select service providers, view service provider information, and view service provider progress. The user module 305 may receive a registration by the user. The registration may be via an internet form, an iOS form, a social media platform (Facebook, twitter, google, etc.). The registration may be via conventional means such as through a targeted offer or mailing sent in an email or letter. The user module 305 may allow and facilitate the user requesting services. The requested services may include but not be limited to one or more of the following: jump start automobile, flat tire change, tow automobile, locked out of car, etc. Additionally, the user module 305 may allow and provide the user to pick a service provide from the provider list received from the service provider server 350. The user module 305 may facilitate and allow the user to view the service provider's specific information. The service provider's specific information may include contact details and estimated time of arrival. The service provider's specific information may also include insurance information and verification data regarding the specific service provider. The user module 305 may also facilitate and allow the user to monitor the service provider's real-time location movement via mapping services and/or the telematics information from the telematics module 315. The user module 305 may also facilitate and allow the user to monitor the service provider's progress of completing the service.

The service provider module 310 may be configured to do one or more of the following: view service request, bid service request, provide confirmation for the service request, and send event notifications (service start, en route, onsite, service complete, canceled service). The service provider module 310 may allow and provide the service provider to view and bid on a service request. The service provider module 310 may also allow and provide the service provider the ability to send event notifications for various service events. For example, the service provider module 310 may send an event notification confirming the service request. The service provider module 310 may also send an event notification for the start and completion of the service request. The service provider module 310 may also send an event notification for other events such as the service provider is en route, the service provider is onsite, or the service provider has canceled the service request.

Additionally, the service provider module 310 may be configured to interface with one or more service provider systems. The service provider module 310 may be configured to provide details of a given service provider, such as location, services provided, service provider ratings, service provider reviews, etc. Additionally, the service provider module 310 may be configured to provide real-time information about a given service provider, such as wait time, service time, service availability, etc. The service provider module 310 may be in communication with the service provider server 350, specifically for the real-time service provider information. Accordingly, a user may be able to receive immediate information about a given service provider through the service provider module 310 of the mobile service provider application 300. Additionally, the service provider module 310 may be configured to provide a qualification, validation, or verification of a given service provider. For example, the service provider module 310 may qualify, validate, or verify the service provider using the insurance information 328 as described and provided by the insurance server 327, such as safe driver information or current payment information. This qualification, validation, and/or verification may provide a pre-screening tool for the users to ensure a quality and safe service provider.

The telematics module 315 may be configured to receive, evaluate, and analyze a user's telematics information, such as location, velocity, direction of travel, route, and destination. The telematics module 315 may further be configured to recommend or provide a ranked list of service providers based on various factors, such as preferred service providers, safest route, fastest route, highest rated service providers, verified service providers, etc. The telematics module 315 may be in communication with the telematics device or in-vehicle device 225, wherein the telematics device 225 sends the telematics information to the telematics module 315. The telematics module 315 may further calculate and provide information regarding distance from nearest service provider to location of the service, time to travel (with or without traffic) from the service provider to location of the service, route information for selected service providers, etc. Additionally, for example, through various driving telematics information devices may provide or know the driving pattern of a user or a service provider. The telematics module 315 may know that the service provider may be driving by the user (service requestor) on their way home from work or through one of their known routes. The telematics module 315 may know and track the routes of the service providers based on the telematics information and the insurance information. The service provider request may be provided based on the known routes of the service provider.

The reward module 320 may be configured to provide a reward depending on the service provider selected by the user and the service utilized by the user. If the user chooses a verified service provider, the reward module 320 and the mobile service provider application 300 may provide a reward, such as cash back, discounts on services, and/or bonus service items. Additionally, the reward module may provide insurance rewards to the user depending on the service provider selected by the user and/or the service provided to the user. The reward module 320 may also provide insurance rewards based on the user's decision to follow the recommendations of the system. The insurance rewards may include discounts on future premiums, increased insurance coverage, and/or decreased deductible.

Additionally, an insurance module 325 may be included with the mobile service provider application 300. The insurance module 325 may include insurance information 328 that may reside on an insurance server 327 regarding information about a particular user, previous accidents, previous claims, information about other users with similar characteristics, etc. The insurance module 325 may be configured to utilize service provider information in rating factors for providing insurance to the user. The insurance module 325 may derive rating factors for providing insurance based on various information, such as which service providers the user utilizes, when the services are requested, and/or what type of services are utilized or provided. Additionally, the insurance module 325 may be configured to utilize the insurance information 328 and specifically the knowledge and information of previous accidents, insurance claims, and driving history to assist in selecting the best known routes or service providers for the user. Additionally, the insurance module 325 may be configured to utilize the insurance information 328 known about a particular user or service provider and the insurance information 328 about users or service providers with similar characteristics to provide a prioritized rank and/or recommendations regarding known routes and service providers utilized. The insurance module 325 and the reward module 320 may be configured to provide a reward depending on the service provider selected by the user and potentially the services utilized by the user. If the user chooses a service provider qualified by the insurance module, the insurance module 325 and reward module 320 may provide an insurance reward, such as a discount on future premiums, increased coverage, or decreased deductibles.

The electronic payment module 330 may be configured to allow for and provide an electronic payment for the services rendered. The electronic payment module 330 may be configured to allow for the electronic payment to be automatic with a pre-entered payment method, such as credit card information, bank information, PayPal, google wallet, etc. With the automatic electronic payment method, the electronic payment module 330 will automatically send the payment information to the service provider server 350 after an order has been placed. Additionally, the electronic payment module 330 may be configured to allow for manual individual input of payment methods with each service provider. In the manual electronic payment method, a service request may not be complete until the user manually inputs payment information to pay for the services. Additionally, the electronic payment module 330 may be configured to provide a yearly membership for the services, whereas the customer does not pay for each individual service request.

The evaluation module 335 may be configured to allow and provide evaluations, ratings, and comments for the users and the service providers. The evaluation module 335 may provide the user with the ability to submit an evaluation/feedback of the service provider. The evaluation module 335 may also provide the service provider with the ability to submit evaluation/feedback of the user. The evaluation module 335 may include a simple form to rate the service provider and/or the user. The evaluation module 335 may utilize ratings such at excellent, very good, good, or poor. A numerical rating system may be utilized as well, such as a ranking from 1 to 5 or 1 to 10. The evaluation module 335 may also provide a comments section for the user or service provider to leave for the given service request. The evaluation module 335 may also consolidate, record, and present the various ratings for each service provider and user such that the service providers and users can view this data and use this data in order to make future decisions with providing services.

The steps that follow in FIG. 4 may be implemented by one or more of the components in FIGS. 1 through 3 and/or other components, including other computing devices. FIG. 4 illustrates an example process 400 by which a user may utilize a computer-implemented method and system and a mobile service provider application 300. The mobile service provider application 300 may be located on a user's mobile device 215, such a cell phone, a smart phone, or tablet/laptop computer. The computer-implemented method and system and the mobile service provider application 300 may also be able to be utilized via any internet connection on a given website or through an internet application. The mobile service provider application 300 may also be located on a vehicle's on-board computer or navigation system. The mobile service provider application 300 may be configured to allow for individuals to be non-professional service providers. The mobile service provider application 300 may include the use of an application on a mobile device that provides telematics information, service provider information to locate the service providers; prioritizes the service providers based on the user preferences, telematics information, and service provider information; and facilitates the service provider request and the electronic payment for the services. The mobile service provider system 100 may allow the individual to register as a service provider and include their skills. The mobile service provider system 100 may provide a performance rating and/or user comments for the service providers. When a user needs services, such as a tire repair, the mobile service provider system 100 may notify the service providers that meet predetermined criteria and allows them to bid on the services. The mobile service provider system 100 may then select a service provider or allows the user to select the service provider. The mobile service provider system 100 can include roadside services, automobile services, home services, and personal services. Telematics information regarding the user and/or the vehicle may be utilized to provide information regarding the service provider's location, velocity (instantaneous and average), route, and destination. The computer-implemented method and system may utilize insurance information to provide additional features and to enhance the mobile service provider methods and systems by providing known and safe routes and recommendations to the user as described and detailed below.

In step 405, the mobile service provider system 100 may receive a registration from a user. In this step 405, the user may register for the mobile service provider application 300 on a mobile device 215, such as a cell phone, a smart phone, or a tablet/laptop computer to register. The user may register via an internet form, an iOS form, a social media platform (Facebook, twitter, google, etc.). The registration may be via conventional means such as through a targeted offer or mailing sent in an email or letter. Furthermore, the mobile service provider system 100 may validate or qualify a user using the insurance information. For example, the mobile service provider system 100 may qualify, validate, or verify the user utilizing the insurance information 328 as described and provided by the insurance server 327, such as safe driver information or current payment information. This qualification, validation, and/or verification may provide a pre-screening tool of the users.

In step 410, the mobile service provider system 100 may receive a registration from a service provider. In this step 410, a service provider may register as a possible service provider for a given service. The service provider may list or check the various services that the service provider can perform and assist with. The service provider may register via the mobile service provider application 300 on a mobile device 215, such as a cell phone, a smart phone, or a tablet/laptop computer to register. The service provider may also register via an internet form, an iOS form, a social media platform (Facebook, twitter, google, etc.). The registration may be via conventional means such as through a targeted offer or mailing sent in an email or letter. Furthermore, the mobile service provider system 100 may validate or qualify a service provider using the insurance information. For example, the mobile service provider system 100 may qualify, validate, or verify the service provider utilizing the insurance information 328 as described and provided by the insurance server 327, such as safe driver information or current payment information. This qualification, validation, and/or verification may provide a pre-screening tool of the service providers thereby providing a pre-scanned non-professional service provider to the users.

In step 415, the mobile service provider system 100 may receive a service request from the user. The service request may be in the form of an online form, via a mobile device 215, etc. In this step 415, the user selects one of the various services provided by the mobile service provider system 100. For example, the services may include roadside services, automobile services, home services, and personal services. Roadside services may include, but not be limited to flat tire assistance, towing services, and fuel services. Automobile services may include, but not be limited to automobile repairs, oil changes, scheduled maintenance appointments, etc. Home services may include, but not be limited to lawn services, landscaping services, window washing services, handyman services, cleaning services, gutter cleaning services, tree removal services, construction services, etc. Personal services may include, but not be limited to salon services, sober driving services, etc. Additionally, in this step 415, the user may suggest a price for the service or a price range for the service.

In step 420, the mobile service provider system 100 may provide the service request to a set of service providers. In this step 420, the mobile service provider system 100 sends the service request to a set of service providers who meet the requirements of the user request. For example, the mobile service provider system 100 may determine one or more service providers that can meet the service request provided by the user. The mobile service provider system 100 may utilize various information to assist with matching the service providers and the user. The mobile service provider system 100 may search and identify any available professional service providers. The mobile service provider system 100 may search and identify any available non-professional providers based on the preferences of the user requesting the services and the service providers.

Additionally, in this step 420, the telematics information of the service providers and the user may be sent from a telematics device 225 located in the vehicle or as part of the mobile device 215. The telematics information may include information regarding the user and/or the user's vehicle. The telematics information may also include information regarding the service provider and/or the service provider's vehicle. The telematics information may include information such as location, velocity (both instantaneous and/or average), direction of travel, route and final destination. This telematics information may then be utilized to assist in providing further information to the mobile service provider system 100 and the mobile service provider application 300. Utilizing telematics information and/or insurance information (driving habits), the mobile service provider system 100 may know the driving routes and the known locations of various service providers when the service request is made and may therefore match up given service providers who are located advantageously to the location that the services will be performed.

In step 425, the mobile service provider system 100 may receive bids from the service providers for the service request. In this step 425, the service provider may review the service request and provide a bid for completing the service request. If the user has requested a specific price or price range, the service provider will either accept or reject the service request at the user's requested price. Additionally, the mobile service provider system 100 may utilize a pre-negotiated rate for a type of service and the service provider will then either accept or reject the service request at the pre-negotiated rate.

In step 430, the mobile service provider system 100 may provide service provider information to the user. In this step 430, the mobile service provider system 100 may provide a prioritized ranking of the service providers based on telematics information and the service request. For example, if the service request includes a flat tire request, the system will provide a prioritized ranking of flat tire service providers closest to the user and based on the service providers known direction of travel and or route/destination. Additionally, based on the telematics data and the service request, the mobile service provider system 100 may know where the user is located and the location and the direction of travel of the service providers and therefore provide the safest route and/or the shortest route for the service provider and/or a prioritized list of those service providers. Additionally, based on the telematics data and the service request, the mobile service provider system 100 may provide a list of the highest ranked or highest rated service providers for the prioritized list of services.

In step 435, the mobile service provider system 100 may receive a selected service provider from the user. In this step 435, the mobile service provider system 100 may either select the service provider for the user or allow the user to select the service provider. The mobile service provider system 100 may determine a prioritized ranking of service provider based on one or more of the following: the telematics information, insurance information, and the service request. Additionally, mobile service provider system 100 may utilize the bid price of the service and timing of the starting and completing the service request when selecting the service provider. Additionally, the mobile service provider system 100 may provide the user with a number of different options of service providers, such as three service providers and allow the user to select which service provider they would like. The user may be given different pricing and timing based on different potential service providers. In different situations, cost may be less significant and convenience or timing may become more significant. The user may be able to select these features to assist with selecting the service provider.

In step 440, the mobile service provider system 100 may receive confirmation of the service request from the service provider. In this step 440, after the service provider has been selected, the service provider will then confirm the service request, confirm the pricing, and confirm the start and completion time/date for the service request. The mobile service provider system 100 may receive this confirmation from the service provider.

In step 445, the mobile service provider system 100 may provide event notifications for the services provided. In this step 445, the mobile service provider system 100 may provide various service notifications from the service provider to the user. The mobile service provider system 100 may provide the user with information regarding the status of the services, i.e. service confirmation, start time, service provider en-route, service provider onsite, service completed, and/or service canceled.

In step 450, the mobile service provider system 100 may provide an electronic payment for the services. In this step 450, the mobile service provider system 100 may also provide an electronic payment for the services to the service provider server 350. The electronic payment may be made automatically to the service provider server 350 and facilitated by the user entering their payment information into the mobile service provider application 300 during a set-up portion of the application. The electronic payment may also be made to the service provider server 350 manually for an individual order by entering the payment information when the order is placed. Additionally, the electronic payment may also be made for a yearly membership for the services, whereas the customer does not pay for each individual service request.

In step 455, the mobile service provider system 100 may receive a service provider evaluation from the user. In this step 455, the mobile service provider system 100 may allow and provide evaluations, ratings, and comments for the users to complete on the service provider. The mobile service provider system 100 may provide the user with the ability to submit an evaluation/feedback of the service provider. The evaluation may include a simple form to rate the service provider. The evaluation may utilize ratings such at excellent, very good, good, or poor. A numerical rating system may be utilized as well, such as a ranking from 1 to 5 or 1 to 10. The evaluation may also provide a comments section for the user to leave for the given service request. The evaluation may also be saved, consolidated, and recorded for the various ratings for each service provider such that the users can view this data and use this data in order to make future decisions with providing services.

In step 460, the mobile service provider system 100 may receive a user evaluation from the service provider. In this step 460, the mobile service provider system 100 may allow and provide evaluations, ratings, and comments for the service provider to complete on the user. The mobile service provider system 100 may provide the service provider with the ability to submit an evaluation/feedback of the user and the experience and transaction with the user. The evaluation may include a simple form to rate the user. The evaluation may utilize ratings such at excellent, very good, good, or poor. A numerical rating system may be utilized as well, such as a ranking from 1 to 5 or 1 to 10. The evaluation may also provide a comments section for the service provider to leave for the given service request. The evaluation may also be saved, consolidated, and recorded for the various ratings for each user such that the service providers can view this data and use this data in order to make future decisions with providing services.

According to some arrangements, the process described with respect to FIG. 4 may be provided by a mobile service provider application 300 executing on a device such as a user's mobile communication device 215, through the internet or on a webpage, or a user's vehicle computer or navigation system.

As was described above, the insurance module 325 may be utilized with the computer-implemented method and system and a mobile service provider application. The steps that follow in FIG. 5 may be implemented by one or more of the components in FIGS. 1 through 3 and/or other components, including other computing devices. FIG. 5 illustrates an example process 500 by which a user may utilize a computer-implemented method and system and a mobile service provider application 300 with insurance aspects. The mobile service provider application 300 may be located on a user's mobile device 215, such a cell phone, a smart phone, or tablet/laptop computer. The computer-implemented method and system and the mobile service provider application 300 may also be able to be utilized via any internet connection on a given website or through an internet application. The mobile service provider application 300 may also be located on a vehicle's on-board computer or navigation system. The mobile service provider application 300 may be configured to allow for individuals to be non-professional service providers. The mobile service provider application 300 may include the use of an application on a mobile device that provides telematics information, service provider information to locate the service providers; prioritizes the service providers based on the user preferences, telematics information, and service provider information; and facilitates the service provider request and the electronic payment for the services. The mobile service provider system 100 may allow the individual to register as a service provider and include their skills. The mobile service provider system 100 may provide a performance rating and/or user comments for the service providers. When a user needs services, such as a tire repair, the mobile service provider system 100 may notify the service providers that meet predetermined criteria and allows them to bid on the services. The mobile service provider system 100 may then select a service provider or allows the user to select the service provider. The mobile service provider system 100 can include roadside services, automobile services, home services, and personal services. Telematics information regarding the user and/or the vehicle may be utilized to provide information regarding the service provider's location, velocity (instantaneous and average), route, and destination. The computer-implemented method and system may utilize insurance information to provide additional features and to enhance the mobile service provider methods and systems by providing known and safe routes and recommendations to the user as described and detailed below.

In step 505, the mobile service provider system 100 may receive a registration from a user. In this step 405, the user may register for the mobile service provider application 300 on a mobile device 215, such as a cell phone, a smart phone, or a tablet/laptop computer to register. The user may register via an internet form, an iOS form, a social media platform (Facebook, twitter, google, etc.). The registration may be via conventional means such as through a targeted offer or mailing sent in an email or letter. Furthermore, the mobile service provider system 100 may validate or qualify a user using the insurance information. For example, the mobile service provider system 100 may qualify, validate, or verify the user utilizing the insurance information 328 as described and provided by the insurance server 327, such as safe driver information or current payment information. This qualification, validation, and/or verification may provide a pre-screening tool of the users.

In step 510, the mobile service provider system 100 may receive a registration from a service provider. In this step 510, a service provider may register as a possible service provider for a given service. The service provider may list or check the various services that the service provider can perform and assist with. The service provider may register via the mobile service provider application 300 on a mobile device 215, such as a cell phone, a smart phone, or a tablet/laptop computer to register. The service provider may also register via an internet form, an iOS form, a social media platform (Facebook, twitter, google, etc.). The registration may be via conventional means such as through a targeted offer or mailing sent in an email or letter. Furthermore, the mobile service provider system 100 may validate or qualify a service provider using the insurance information. For example, the mobile service provider system 100 may qualify, validate, or verify the service provider utilizing the insurance information 328 as described and provided by the insurance server 327, such as safe driver information or current payment information. This qualification, validation, and/or verification may provide a pre-screening tool of the service providers thereby providing a pre-scanned non-professional service provider to the users.

In step 515 the mobile service provider system 100 may also provide insurance information 328 regarding the service providers and the users. Insurance information 328 may be utilized with the computer-implemented method and system that may reside on an insurance server 327. The insurance information 328 may include information about a particular user or service provider, location and instances of previous accidents, locations and instances of previous claims, driving history, and information about other users and service providers with similar characteristics, etc.

In addition to step 515, the mobile service provider system 100 may provide additional ranking of service providers based on the insurance information 328. The mobile service provider system 100 may use the insurance information 328 of previous accident locations, driving history, and claims to assist in selecting the route from the service provider to a location of the service request. The mobile service provider system 100 may provide recommendations for the safest routes and rate the routes and the potential service providers based on the previous accidents, driving history, and claims in the insurance information 328.

The mobile service provider system 100 may also use the insurance information 328 of the particular user and information about users with similar characteristics to provide recommendations regarding routes and service request locations. Based on the user and service provider characteristics and past behavior, the mobile service provider system 100 may prioritize a list of potential service providers or routes for the selected service provider that the system determines will best meet the preferences of the user.

In step 520, the mobile service provider system 100 may receive a service request from the user. The service request may be in the form of an online form, via a mobile device 215, etc. In this step 520, the user selects one of the various services provided by the mobile service provider system 100. For example, the services may include roadside services, automobile services, home services, and personal services. Roadside services may include, but not be limited to flat tire assistance, towing services, and fuel services. Automobile services may include, but not be limited to automobile repairs, oil changes, scheduled maintenance appointments, etc. Home services may include, but not be limited to lawn services, landscaping services, window washing services, handyman services, cleaning services, gutter cleaning services, tree removal services, construction services, etc. Personal services may include, but not be limited to salon services, sober driving services, etc. Additionally, in this step 520, the user may suggest a price for the service or a price range for the service.

In step 525, the mobile service provider system 100 may provide the service request to a set of service providers. In this step 525, the mobile service provider system 100 sends the service request to a set of service providers who meet the requirements of the user request. For example, the system may determine one or more service providers that can meet the service request provided by the user. The mobile service provider system 100 may utilize various information to assist with this matching the service providers and the user. The mobile service provider system 100 may search and identify any available professional service providers. The mobile service provider system 100 may search and identify any available non-professional providers based on the preferences of the user requesting the services and the service providers.

Additionally, in this step 525, the telematics information of the service providers and the user may be sent from a telematics device 225 located in the vehicle or as part of the mobile device 215. The telematics information may include information regarding the user and/or the user's vehicle. The telematics information may also include information regarding the service provider and/or the service provider's vehicle. The telematics information may include information such as location, velocity (both instantaneous and/or average), direction of travel, route and final destination. The mobile service provider system 100 may then utilize the telematics information to assist in providing further information to the system and the mobile service provider application 300. Utilizing telematics information and/or insurance information (driving habits), the mobile service provider system 100 may know the driving routes and the known locations of various service providers when the service request is made and may therefore match up given service providers who are located advantageously to the location that the services will be performed.

In step 530, the mobile service provider system 100 may receive bids from the service providers for the service request. In this step 530, the service provider may review the service request and provide a bid for completing the service request. If the user has requested a specific price or price range, the service provider will either accept or reject the service request at the user's requested price. Additionally, the mobile service provider system 100 may utilize a pre-negotiated rate for a type of service and the service provider will then either accept or reject the service request at the pre-negotiated rate.

In step 535, the mobile service provider system 100 may provide service provider information to the user. In this step 535, the mobile service provider system 100 may provide a prioritized ranking of the service providers based on telematics information and the service request. For example, if the service request includes a flat tire request, the system will provide a prioritized ranking of flat tire service providers closest to the user and based on the service providers known direction of travel and or route/destination. Additionally, based on the telematics data and the service request, the mobile service provider system 100 may know where the user is located and the location and the direction of travel of the service providers and therefore provide the safest route and/or the shortest route for the service provider and/or a prioritized list of those service providers. Additionally, based on the telematics data and the service request, the mobile service provider system 100 may provide a list of the highest ranked or highest rated service providers for the prioritized list of services.

In step 540, the mobile service provider system 100 may receive a selected service provider from the user. In this step 540, the mobile service provider system 100 may either select the service provider for the user or allow the user to select the service provider. The system may determine a prioritized ranking of service provider based on one or more of the following: the telematics information, insurance information, and the service request. Additionally, the mobile service provider system 100 may utilize the bid price of the service and timing of the starting and completing the service request when selecting the service provider. Additionally, the mobile service provider system 100 may provide the user with a number of different options of service providers, such as three service providers and allow the user to select which service provider they would like. The mobile service provider system 100 may send the user different pricing and timing based on different potential service providers. In different situations, cost may be less significant and convenience or timing may become more significant. The user may be able to select these features to assist with selecting the service provider.

In step 545, the mobile service provider system 100 may receive confirmation of the service request from the service provider. In this step 545, after the service provider has been selected, the service provider will then confirm the service request, confirm the pricing, and confirm the start and completion time/date for the service request. The mobile service provider system 100 may receive this confirmation from the service provider.

In step 550, the mobile service provider system 100 may provide event notifications for the services provided. In this step 550, the mobile service provider system 100 may provide various service notifications from the service provider to the user. The mobile service provider system 100 may provide the user with information regarding the status of the services, i.e. service confirmation, start time, service provider en-route, service provider onsite, service completed, and/or service canceled.

In step 555, the mobile service provider system 100 may provide an electronic payment for the services. In this step 555, the mobile service provider system 100 may also provide an electronic payment for the services to the service provider server 350. The electronic payment may be made automatically to the service provider server 350 and facilitated by the user entering their payment information into the mobile service provider application 300 during a set-up portion of the application. The electronic payment may also be made to the service provider server 350 manually for an individual order by entering the payment information when the order is placed. Additionally, the electronic payment may also be made for a yearly membership for the services, whereas the customer does not pay for each individual service request.

In step 560, the mobile service provider system 100 may provide rewards to the user depending on the service provider chosen by the user and/or the services provided to the user. The mobile service provider system 100 may also provide rewards based on the user's decision to follow the recommendations of the system. The rewards may include cash back, a reward with the service provider, a discount with the service provider, and/or bonus services. Additionally, the mobile service provider system 100 may provide insurance rewards to the user depending on the service provider chosen by the user and/or the services provided to the user. The mobile service provider system 100 may also provide insurance rewards based on the user's decision to follow the recommendations of the system. The insurance rewards may include discounts on future premiums, increased insurance coverage, and/or decreased deductible.

In step 565, the mobile service provider system 100 may receive an evaluation from a user and/or a service provider. In this step 565, the mobile service provider system 100 may allow and provide evaluations, ratings, and comments for the users/service providers to complete on the service request. The mobile service provider system 100 may provide the user/service providers with the ability to submit an evaluation/feedback of the service request. The evaluation may include a simple form to rate the service request. The evaluation may utilize ratings such at excellent, very good, good, or poor. The evaluation may also utilize a numerical rating system, such as a ranking from 1 to 5 or 1 to 10. The evaluation may also provide a comments section for the user/service provider to leave for the given service request. The mobile service provider system 100 may save, consolidate, and record the evaluation reports for the various ratings for each user/service provider such that future users and service providers can view this data and use this data in order to make future decisions with future service requests.

According to some arrangements, the process described with respect to FIG. 5 may be provided by a mobile service provider application 300 executing on a device such as a user's mobile communication device 215 through the internet or on a webpage, or a user's vehicle computer or navigation system.

According to another aspect of this invention, the mobile service provider system 100 may optimize job assignments of the service providers based on knowing where the service providers are located—such as tow trucks. In this example, the mobile service provider system 100 may know where the tow trucks of a given service provider are located. The mobile service provider system 100 may then optimize the job assignments, routes and jobs, of this service provider by knowing where the tow truck is located. Additionally, to further optimize the job assignments, the mobile service provider system 100 may pre-position tow trucks in a particular geo-reference based on the past history of needed and known repairs (utilizing the insurance information as presented previously). While this example utilized tow trucks as the service provided, this job assignment optimization feature could be utilized with any given service provider in a similar manner.

According to another aspect of this invention, mobile service provider system 100 may include various rules criteria and evaluation for the mobile service provider system 100. For example, for initial service provider selection, the following rules criteria and evaluation may be utilized: the distance from the service provider to the user, the service provider's availability (whether the service provider is logged on), and the service type requested. In another example, for second service provider selection, the total distance may be a rules criteria and evaluation—meaning that the service provider is available however working at a different service request. The mobile service provider system 100 may then calculate the actual distance including the current service destination and then the future service destination between the previous service designation and the current user location. In another example, for a third provider selection after the bid, the mobile service provider system 100 may select one professional, one up-sell offer, and N number of non-professional service providers. The mobile service provider system 100 may then utilized the following rules criteria and evaluation: cost, total service distance (current location+current service destination, if any+new customer location+new customer final destination), estimated time of arrival, service ratings and performance ratings, and service provider company (reviewing any preferred vendors).

In another aspect of the invention, the mobile service provider system 100 may include capabilities in handling exception conditions. Exception conditions may happen during the overall process execution which require some kind of manual intervention. Some example exception conditions may include: the service provider cannot service the service request after acceptance, the user cancels the service request without informing the mobile service provider system 100 or the service provider, the service provider cannot find the user or the location of the service request, there is a service mismatch between what's ordered and what is needed, damaged property during the service, or the user complains that the service level agreement (SLA) is not met.

In another aspect of the invention, the mobile service provider system 100 may include capabilities in handling external special events. Special events may be those external events that impact the overall service fulfillment. Some example special events may include: large number of service requests anticipating due to weather, historical patterns, special events such as games, New Year, etc.; and large anticipated service request that is too difficult to handle.

In another embodiment in accordance with aspects of this invention, FIGS. 6 through 8 illustrate a roadside assistance service provider system 600 that may be utilized for the assignment of roadside assistance service providers, such as tow trucks, to distressed vehicles/drivers requiring roadside assistance. Though some prior art systems might automatically assign tow truck drivers based just on the proximity to a distressed vehicle, the roadside assistance service provide system 600 takes a more sophisticated approach to collecting various types of data through sensors and systems, analyzing that data, and assigning truck drivers based on a complex plurality of factors and characteristics for a more optimized assignment. It is understood to one skilled in the art that the embodiment described and disclosed above and in FIGS. 1-5 may be used together with these embodiment illustrated in FIGS. 6-8 and described below.

Generally the roadside assistance service provider system 600 may include a collection module 610, an assignment module 620, and a feedback module 630. In the collection module 610 (or gathering/collection module), sensors on a tow truck or other similar vehicles (e.g. whether the flatbed is down, GPS location monitoring, etc.), smartphone user interfaces, and historical statistics about roadside assistance services (e.g. the historical average time for changing a flat tire, for jumping a dead battery, etc.) may be collected from the real world and stored in a data store, then analyzed using particular rules and/or formats. In the assignment module 620, particular roadside assistance service providers may be assigned to particular distressed vehicles/drivers based on one or more characteristics, including characteristics/rules from the collection module 610. For example, the assignment module 620 may match/assign a driver that only speaks Polish with a tow truck driver that understands Polish. Other characteristics/criteria utilized by the assignment module 620 may include proximity in location, prior user ratings, equipment on the tow truck, skillset/expertise of the driver of the tow truck, price/cost of the tow truck roadside assistance services, etc. The feedback/display module 630 may provide near real-time cues to the tow truck driver's mobile device, such as alerting when the amount of time spent on a task exceeds a predefined threshold, flagging high priority tasks/assignments, providing a step-by-step checklist for the repair, etc., and award points/score to the tow truck driver.

FIG. 6 is an example block diagram of the roadside assistance service provider system 600 and a roadside assistance service provider server 605. The roadside assistance service provider server 605 may include a variety of software or firmware modules such as one or more of the following: a collection module 610, an assignment module 620, a feedback module 630, a reward module 640, and an insurance module 650. Each of these modules may be utilized by the roadside assistance service provider server 605.

Generally, the collection module 610 collects roadside assistance service provider information from real-world and stores the information in a database 121 that may then be analyzed using particular rules and formulas. The roadside assistance service provider information may be collected from sensors on a tow truck or other vehicles, such as whether the flatbed is down, GPS location monitoring, etc. The roadside assistance service provider information may also be collected from smartphone user interfaces. Additionally, the collection module 610 may collect historical statistics about roadside assistance services, such as the historical average time for changing a flat tire, for jumping a dead battery, etc. Further, the collection module 610 may collect roadside assistance information. The roadside assistance information may include and not be limited to: real-time equipment information, real-time GPS information, historical statistical data for various tasks and/or roadside assistance services. This roadside assistance information may then be stored in a database 121 and then analyzed using particular rules, formulas or other factors or characteristics. The collection module 610 may be configured to do one or more of the following: receive roadside assistance service request and collect information to verify roadside assistance service request criteria.

The collection module 610 may allow and facilitate the user requesting services. The requested services may include but not be limited to one or more of the following jobs or tasks: jump start automobile, flat tire change, tow automobile, locked out of car, etc. The collection module 610 may also collect information to verify every new roadside assistance service request to ensure the request meets particular criteria. For example, the collection module 610 may verify that the roadside assistance service request or task is not currently assigned. The collection module 610 may also verify that the roadside assistance service provider is not enrolled in auto-assignment. The collection module 610 may also verify the roadside assistance service providers that are logged-in and available. Any driver or roadside assistance service provider logged into the roadside assistance service provider system 600 may be considered in the list of roadside assistance service providers for a given job or task. Additionally, the collection module 610 may be configured to provide a qualification, validation, or verification of a given roadside assistance service provider. For example, the collection module 610 may qualify, validate, or verify the roadside assistance service provider using the insurance information 665 as described and provided by the insurance server 660, such as safe driver information or current payment information. This qualification, validation, and/or verification may provide a pre-screening tool for the roadside assistance service providers to ensure a quality and safe roadside assistance service provider.

The collection module 610 may also receive a registration by the roadside assistance service provider. The registration may be via a mobile application, a web component, an internet form, an iOS form, a social media platform (Facebook, twitter, google, etc.). The registration may be via conventional means such as through a targeted offer or mailing sent in an email or letter.

The collection module 610 may also include various sensors and other information regarding the vehicles and tow trucks. For example, various sensors may be located on a tow truck or other vehicles. The sensors may provide information such as whether the flatbed is down, the GPS location, or other similar information. The collection module 610 may be configured to receive, evaluate, and analyze a roadside assistance service provider's telematics information, such as location, velocity, direction of travel, route, and destination, as well as the distressed vehicle's location, velocity, direction of travel, route, and destination. Once a service is requested, the collection module 610 may also determine the amount of time for each task for the requested roadside assistance service necessary for a given roadside assistance service provider, for example getting fuel will take 5 minutes for all drivers. The collection module 610 may aggregate the time from many different drivers and service providers. The roadside assistance service provider system 600 and collection module 610 may learn from driver's or service provider's history as to the amount of time it takes to engage and complete a particular task. This information may later be utilized in the assignment module 615 in helping to assign the roadside assistance service provider to a roadside assistance service request. Additionally, the collection module 610 may include various industry estimates for tasks and subtasks for given roadside assistance services and this information may be utilized for driver customization during the assignment process with the assignment module 615. Additionally, historical statistics about roadside assistance services such as the historical average for a given task, such as changing a flat tire, or jumping a dead battery, etc, may be collected from the real world and stored in a database. This information may then be analyzed using particular rules and formulas to determine the roadside assistance service providers.

Additionally, the collection module 610 may be configured to interface with one or more other roadside assistance service provider systems. The collection module 610 may be configured to provide details of a given roadside assistance service provider, such as location, services provided, roadside assistance service provider ratings, roadside assistance service provider reviews, etc. Additionally, the collection module 610 may be configured to provide real-time information about a given roadside assistance service provider, such as wait time, service time, service availability, etc. The collection module 610 may provide real-time roadside assistance service provider information.

Generally, the assignment module 615 may assign particular roadside assistance service providers to particular distressed vehicles/drivers based on one or more characteristics, including characteristics/rules from the collection module 610. The assignment module 615 may be configured to do one or more of the following: compare existing workload, timelines, and distance for each roadside assistance service provider and requested service; rank roadside assistance service providers; and provide assignments and invitations to roadside assistance service providers.

The assignment module 615 may compare the existing workload, timelines, and distances for each of the various roadside assistance service providers and the requested service. The assignment module 615 may utilize many factors, such as considering the current queue and the amount of time to complete tasks in the queue. The assignment module 615 may also consider and factor the skill levels required to complete a given task, for example a skill level 1 may use a factor of 2 for time estimates. The assignment module 615 may also consider and factor the skill level and whether a driver or roadside assistance service provider is allowed and/or capable of working on a specific job or task, utilizing it as a qualifier. The assignment module 615 may also consider and factor the price of the driver, any particular skills of the driver, the match with the user or customer, and the equipment of the driver. The assignment module 615 may also consider how long the driver will take at their current job, utilizing information from the collection module 610. The assignment module 615 may also consider weather, time of day, traffic, neighborhood, type of road, etc. which may cause the tasks onsite to take longer to perform. The assignment module 615 may also utilize driver performance as a factor in assignment of the next jobs and prioritize tasks at which a certain driver is strong. Other factors and/or considerations may be utilized for assigning roadside assistance service providers without departing from this invention.

Additionally, the assignment module 615 may rank the roadside assistance service providers. The rankings may be based on time, then by distance if there is a tie, and then by on time performance if there is still a tie. Other rankings may be utilized for the roadside assistance service providers without departing from this invention. Following the rankings, the assignment module 615 may then send invitations and or assignments to the drivers or the roadside assistance service provider. If the driver accepts the invitation and assignment, the assignment module 615 may assign the roadside assistance service request to the driver. If the driver does not accept the invitation and assignment, the assignment module 615 may send the roadside assistance service request to the next driver or roadside assistance service provider on the list. Additionally, if there is no assignment after a given time frame (for example 10 minutes), then the assignment module 615 may send the roadside assistance service request back to a manual dispatcher for manual assignment.

Additionally, the assignment module 615 may be utilized for reassignment of a roadside assistance service request. During a reassignment, the assignment module 615 may shuffle the assignments during the middle of the assignment process. Current workloads may be shuffled as long as the driver or roadside assistance service provider is not yet at the roadside assistance site. Various situations may trigger the reassignment. One situation that may trigger a reassignment may be the flagging of a roadside assistance service request as a priority roadside assistance service in which particular jobs may override other jobs and may be highlighted to dynamically reassign jobs. One example of this priority flagging reassignment may be a person stranded on a highway and needs attention immediately. Another example of this priority flagging reassignment may be a person or distressed vehicle stranded in a dangerous location and needing attention immediately. Another situation that may trigger a reassignment may be the shifting of work to other roadside assistance service providers in a particular roadside assistance service provider is moving slowly during a given day. In this instance, a centralized screen or output may be utilized to show how different roadside assistance service providers are working and performing.

Additionally, the assignment module 615 may facilitate and allow the user to view the service provider's specific information. The service provider's specific information may include contact details and estimated time of arrival. The service provider's specific information may also include insurance information and verification data regarding the specific service provider.

Additionally, the assignment module 615 may be configured to do one or more of the following: view service request, bid service request, provide confirmation for the service request, and send roadside assistance event notifications (service start, en route, onsite, service complete, canceled service). The assignment module 615 may allow and provide the service provider to view and bid on a service request. The assignment module 615 may also allow and provide the service provider the ability to send roadside assistance event notifications for various service events. For example, the assignment module 615 may send an event notification confirming the service request. The assignment module 615 may also send an event notification for the start and completion of the service request. The assignment module 615 may also send an event notification for other events such as the service provider is en route, the service provider is onsite, or the service provider has canceled the service request.

The assignment module 615 may further be configured to recommend or provide a ranked list of roadside assistance service providers based on various factors, such as preferred roadside assistance service providers, safest route, fastest route, highest rated roadside assistance service providers, verified roadside assistance service providers, etc. The assignment module 615 may be in communication with the telematics device or in-vehicle device 225, wherein the telematics device 225 sends the telematics information to the assignment module 615.

Additionally, the assignment module 615 may further calculate and provide information regarding distance from nearest roadside assistance service provider to location of the service, time to travel (with or without traffic) from the roadside assistance service provider to location of the roadside assistance service, route information for selected roadside assistance service providers, etc. Additionally, for example, through various driving telematics information devices may provide or know the driving pattern of a user or a roadside assistance service provider. The assignment module 615 may know that the roadside assistance service provider may be driving by the user (service requestor) on their way home from work or through one of their known routes. The assignment module 315 may know and track the routes of the roadside assistance service providers based on the telematics information and the insurance information. The roadside assistance service provider request may be provided based on the known routes of a given roadside assistance service provider.

Generally, the feedback module 620 may provide near real-time cues to the tow truck driver's mobile device, such as alerting when the amount of time spent on a task exceeds a predefined threshold, flagging high priority tasks/assignments, providing a step-by-step checklist for the repair, etc., and award points/score to the tow truck driver. The feedback module 620 may be configured to do one or more of the following: provide roadside assistance event notifications for the services provided, provide rewards based on the roadside assistance service provided, and provide performance feedback for roadside assistance service providers. The feedback module 620 may provide feedback through a display.

As the drivers are progressing through a job or a roadside assistance service request, the feedback module 620 may provide status updates of the progress. The drivers may also update their status through the feedback module 620. The feedback module 620 may utilize telematics information to update and provide the notification of an updated status. The feedback module 620 may also utilized other information from the sensors that the tow has been activated or that the tow bed has been lowered to update and provide the notification of an updated status. A reminder or status update may pop-up as a visual indicator. The feedback module 620 may provide a reminder to tell the driver when the driver has gone beyond the average time for a particular task, and this task may be listed in red to signify that the driver is over the time. The feedback module 620 may also display a list of the tasks and the average time for each task. The driver may see these events or tasks in sequence. Additionally, the feedback module 620 may display or report that the driver is over or under a given time.

The feedback module 620 may also include a performance output or screen, which displays to the driver whether the driver is within their estimated time of arrival for meeting their roadside assistance service request. The feedback module 620 may also display or output to the driver whether the driver's performance meets average performance as well as the driver's past performance for the given tasks or roadside assistance services. The feedback module 620 may also calculate a performance score based on the given tasks or roadside assistance services. The feedback module 620 may output or display the driver's performance score that depends on the driver's ability to meet the timing of tasks as estimated or required. The feedback module 620 may also be able to identify a driver that performs weak at certain tasks for training the driver in those given tasks.

The feedback module 620 may provide a service provider or a user the ability to receive immediate information about a given roadside assistance service provider through the roadside assistance service feedback module 620. The feedback module 620 may also facilitate and allow the user to monitor the service provider's real-time location movement via mapping services and/or the telematics information from the telematics device 225. The feedback module 620 may also facilitate and allow the user to monitor the service provider's progress of completing the service.

The reward module 640 may be configured to provide a reward to an individual driver or roadside assistance service provider or roadside assistance service provider company if particular times are met. For example, the reward may allow a driver to move up in a queue in a definitive way if the roadside assistance service provider beats the estimate time or suggested times. Additionally, the reward module 640 may provide an individual driver or roadside assistance service provider an additional award if the job or tasks are done more quickly. The reward module 640 may provide awards based on accurate estimates and not necessarily doing a job or task more quickly.

Additionally, an insurance module 650 may be included with the roadside assistance service provider server 605. The insurance module 650 may include insurance information 665 that may reside on an insurance server 660 regarding information about a particular user, previous accidents, previous claims, information about other users with similar characteristics, etc. The insurance module 650 may also include insurance information 665 that may reside on an insurance server 660 regarding information about a particular roadside assistance service provider, previous accidents, previous claims, driving history, any other pertinent information about the roadside assistance service provider, and information about other roadside assistance service providers with similar characteristics, etc. Additionally, the insurance module 650 may work together with the assignment module 620 to utilize the insurance information 665 and specifically the knowledge and information of previous accidents, insurance claims, and driving history to assist in selecting the best known routes or service providers for the user. Additionally, the insurance module 650 may work together with the assignment module 620 to utilize the insurance information 665 known about a particular user or service provider and the insurance information 665 about users or service providers with similar characteristics to provide a prioritized rank and/or recommendations regarding known routes and service providers utilized. The insurance module 650 and the reward module 640 may be configured to provide a reward depending on the roadside assistance service provider performance and providing accurate estimates. For example, if the roadside assistance service provider meets particular times for tasks and/or provides accurate estimates for the tasks and jobs, the insurance module 650 and reward module 640 may provide an insurance reward, such as a discount on future premiums, increased coverage, or decreased deductibles.

The steps that follow in FIG. 7 may be implemented by one or more of the components in FIGS. 1 through 3 and FIG. 6 and/or other components, including other computing devices. FIG. 7 illustrates an example process 700 by which a user may utilize a computer-implemented method and system and a roadside assistance service provider system 600. The roadside assistance service provider system 600 may include sensors on a tow truck or other similar vehicles (e.g. whether the flatbed is down, GPS location monitoring, etc.), smartphone user interfaces and historical statistics about roadside assistance services (e.g. the historical average time for changing a flat tire, for jumping a dead battery, etc.) that may be collected from the real world and stored in a data store, and analyzed using particular rules and/or formats. Particular roadside assistance service providers may be assigned to particular distressed vehicles/drivers based on one or more characteristics, including characteristics/rules. Other characteristics/criteria may include proximity in location, prior user ratings, equipment on the tow truck, skillset/expertise of the driver of the tow truck, price of the tow truck, etc. Additionally, the roadside assistance service provider system 600 may provide near real-time cues to the tow truck driver's mobile device, such as alerting when the amount of time spent on a task exceeds a predefined threshold, flagging high priority tasks/assignments, providing a step-by-step checklist for the repair, etc., and award points/score to the tow truck driver. The computer-implemented method and system may utilize insurance information to provide additional features and to enhance the mobile service provider methods and systems by providing known and safe routes and recommendations to the user as described and detailed below.

In step 705, the roadside assistance service provider system 600 may receive a roadside assistance service request. In this step 705, the roadside assistance service provider system 600 may receive a service request from a customer with a distressed vehicle. The service request may be in the form of an online form, via a mobile device 215, etc. In this step 705, the customer with the distressed vehicle may select one of the various roadside assistance services provided by the roadside assistance service provider system 600. For example, the roadside assistance services may include, but not be limited to flat tire assistance, towing services, fuel services, automobile repairs, oil changes, scheduled maintenance appointments, etc.

Prior to this step, the roadside assistance service provider system 600 may receive a registration from a roadside assistance service provider. A roadside assistance service provider may register as a possible roadside assistance service provider for a given roadside assistance service. The roadside assistance service provider may list or check the various roadside assistance services that the roadside assistance service provider can perform and assist with. The roadside assistance service provider may register via the mobile service provider application 602 on a mobile device 215, such as a cell phone, a smart phone, or a tablet/laptop computer to register. The service provider may also register via an internet form, an iOS form, a social media platform (Facebook, twitter, google, etc.). The registration may be via conventional means such as through a targeted offer or mailing sent in an email or letter.

Additionally, prior to this step, the customer or distressed vehicle may register for the mobile service provider application 602 on a mobile device 215, such as a cell phone, a smart phone, or a tablet/laptop computer to register. The customer or distressed vehicle may register via an internet form, an iOS form, a social media platform (Facebook, twitter, google, etc.). The registration may be via conventional means such as through a targeted offer or mailing sent in an email or letter.

Furthermore, the roadside assistance service provider system 600 may validate or qualify a customer or distressed vehicle or the roadside assistance service provider using the insurance information. For example, the roadside assistance service provider system 600 may qualify, validate, or verify the customer or distressed vehicle or the roadside assistance service provider utilizing the insurance information 665 as described and provided by the insurance server 660, such as safe driver information or current payment information. This qualification, validation, and/or verification may provide a pre-screening tool of the customer or distressed vehicle or the roadside assistance service provider.

In step 710, the roadside assistance service provider system 600 may verify the roadside assistance service request utilizing various criteria. For example, in step 710 the roadside assistance service provider system 600 may verify that the job or task is not currently assigned. The roadside assistance service provider system 600 may also verify that the roadside assistance service provider is not enrolled in auto-assignment. The roadside assistance service provider system 600 may also verify the roadside assistance service providers that are logged-in and available. Any driver or roadside assistance service provider logged into the roadside assistance service provider system 600 may be considered in the list of roadside assistance service providers for a given job or task.

In step 715, the roadside assistance service provider system 600 may compare existing workload, timelines, and distance for each roadside assistance service provider and requested roadside assistance service. In step 715, the roadside assistance service provider system 600 may utilize many factors, such as considering the current queue and the amount of time to complete tasks in the queue. The roadside assistance service provider system 600 may also consider and factor the skill levels required to complete a given task, for example a skill level 1 may use a factor of 2 for time estimates. The roadside assistance service provider system 600 may also consider and factor the skill level and whether a driver or roadside assistance service provider is allowed and/or capable of working on a specific job or task, utilizing it as a qualifier. The roadside assistance service provider system 600 may also consider and factor the price of the driver, any particular skills of the driver, the match with the user or customer, and the equipment of the driver. The roadside assistance service provider system 600 may also consider how long the driver will take at their current job, utilizing information from the collection module 610. The roadside assistance service provider system 600 may also consider weather, time of day, traffic, neighborhood, type of road, etc. which may cause the tasks onsite to take longer to perform. The roadside assistance service provider system 600 may also utilize driver performance as a factor in assignment of the next jobs and prioritize tasks at which a certain driver is strong. Other factors and/or considerations may be utilized for assigning roadside assistance service providers without departing from this invention.

Additionally, in this step 715, the telematics information of the roadside assistance service providers and the user may be sent from a telematics device 225 located in the vehicle or as part of the mobile device 215. The telematics information may include information regarding the user and/or the customer's distressed vehicle. The telematics information may also include information regarding the roadside assistance service provider and/or the roadside assistance service provider's vehicle. The telematics information may include information such as location, velocity (both instantaneous and/or average), direction of travel, route and final destination. This telematics information may then be utilized to assist in providing further information to the roadside assistance service provider system 600. Utilizing telematics information and/or insurance information (driving habits), the roadside assistance service provider system 600 may know the driving routes and the known locations of various roadside assistance service providers when the service request is made and may therefore match up given roadside assistance service providers who are located advantageously to the location that the roadside assistance services will be performed.

In step 720, the roadside assistance service provider system 600 may rank the roadside assistance service providers. The rankings may be based on time, then by distance if there is a tie, and then by on time performance if there is still a tie. The rankings may also be based on any of the factors utilized during step 715. Other rankings may be utilized for the roadside assistance service providers without departing from this invention.

Following the rankings, in step 725, the roadside assistance service provider system 600 may then send invitations and or assignments to the drivers or the roadside assistance service provider. If the driver accepts the invitation and assignment, the roadside assistance service provider system 600 may assign the roadside assistance service request to the driver. If the driver does not accept the invitation and assignment, the roadside assistance service provider system 600 may send the roadside assistance service request to the next driver or roadside assistance service provider on the list. Additionally, if there is no assignment after a given time frame (for example 10 minutes), then the roadside assistance service provider system 600 may send the roadside assistance service request back to a manual dispatcher for manual assignment.

In step 730, the roadside assistance service provider system 600 provides roadside assistance event notifications for the roadside assistance services provided. In step 730, the roadside assistance service provider system 600 may display and or provide feedback for various events and tasks during the roadside assistance services. In this step 730, the roadside assistance service provider system 600 may provide various service notifications from the service provider to the user. The roadside assistance service provider system 600 may provide the user with information regarding the status of the services, i.e. service confirmation, start time, service provider en-route, service provider onsite, service completed, and/or service canceled. Furthermore, in step 730, the roadside assistance service provider system 600, the feedback and display may provide near real-time cues to the tow truck driver's mobile device, such as alerting when the amount of time spent on a task exceeds a predefined threshold, flagging high priority tasks/assignments, providing a step-by-step checklist for the repair, etc., performance measurements, and award points/score to the tow truck driver.

According to some arrangements, the process described with respect to FIG. 7 may be provided by a mobile service provider application 602 or a service provider application executing on a device such as a service provider's mobile communication device 215 or service provider server 605, through the internet or on a webpage, or a service provider's vehicle computer or navigation system.

The steps that follow in FIG. 8 may be implemented by one or more of the components in FIGS. 1 through 3 and FIG. 6 and/or other components, including other computing devices. FIG. 8 illustrates an example process 800 by which a user may utilize a computer-implemented method and system and a roadside assistance service provider system 600. The roadside assistance service provider system 600 may include sensors on a tow truck or other similar vehicles (e.g. whether the flatbed is down, GPS location monitoring, etc.), smartphone user interfaces and historical statistics about roadside assistance services (e.g. the historical average time for changing a flat tire, for jumping a dead battery, etc.) that may be collected from the real world and stored in a data store, and analyzed using particular rules and/or formats. Particular roadside assistance service providers may be assigned to particular distressed vehicles/drivers based on one or more characteristics, including characteristics/rules. Other characteristics/criteria may include proximity in location, prior user ratings, equipment on the tow truck, skillset/expertise of the driver of the tow truck, price of the tow truck, etc. Additionally, the roadside assistance service provider system 600 may provide near real-time cues to the tow truck driver's mobile device, such as alerting when the amount of time spent on a task exceeds a predefined threshold, flagging high priority tasks/assignments, providing a step-by-step checklist for the repair, etc., and award points/score to the tow truck driver. The computer-implemented method and system may utilize insurance information to provide additional features and to enhance the mobile service provider methods and systems by providing known and safe routes and recommendations to the user as described and detailed below.

In step 805, the roadside assistance service provider system 600 may receive a roadside assistance service request. In this step 805, the roadside assistance service provider system 600 may receive a service request from a customer with a distressed vehicle. The service request may be in the form of an online form, via a mobile device 215, etc. In this step 805, the customer with the distressed vehicle may select one of the various roadside assistance services provided by the roadside assistance service provider system 600. For example, the roadside assistance services may include, but not be limited to flat tire assistance, towing services, fuel services, automobile repairs, oil changes, scheduled maintenance appointments, etc.

Prior to this step, the roadside assistance service provider system 600 may receive a registration from a roadside assistance service provider. A roadside assistance service provider may register as a possible roadside assistance service provider for a given roadside assistance service. The roadside assistance service provider may list or check the various roadside assistance services that the roadside assistance service provider can perform and assist with. The roadside assistance service provider may register via the mobile service provider application 602 on a mobile device 215, such as a cell phone, a smart phone, or a tablet/laptop computer to register. The service provider may also register via an internet form, an iOS form, a social media platform (Facebook, twitter, google, etc.). The registration may be via conventional means such as through a targeted offer or mailing sent in an email or letter.

Additionally, prior to this step, the customer or distressed vehicle may register for the mobile service provider application 602 on a mobile device 215, such as a cell phone, a smart phone, or a tablet/laptop computer to register. The customer or distressed vehicle may register via an internet form, an iOS form, a social media platform (Facebook, twitter, google, etc.). The registration may be via conventional means such as through a targeted offer or mailing sent in an email or letter.

Furthermore, the roadside assistance service provider system 600 may validate or qualify a customer or distressed vehicle or the roadside assistance service provider using the insurance information. For example, the roadside assistance service provider system 600 may qualify, validate, or verify the customer or distressed vehicle or the roadside assistance service provider utilizing the insurance information 665 as described and provided by the insurance server 660, such as safe driver information or current payment information. This qualification, validation, and/or verification may provide a pre-screening tool of the customer or distressed vehicle or the roadside assistance service provider.

In step 810, the roadside assistance service provider system 600 may verify the roadside assistance service request utilizing various criteria. For example, in step 810 the roadside assistance service provider system 600 may verify that the job or task is not currently assigned. The roadside assistance service provider system 600 may also verify that the roadside assistance service provider is not enrolled in auto-assignment. The roadside assistance service provider system 600 may also verify the roadside assistance service providers that are logged-in and available. Any driver or roadside assistance service provider logged into the roadside assistance service provider system 600 may be considered in the list of roadside assistance service providers for a given job or task.

In step 815, the roadside assistance service provider system 600 may compare existing workload, timelines, and distance for each roadside assistance service provider and requested roadside assistance service. In step 815, the roadside assistance service provider system 600 may utilize many factors, such as considering the current queue and the amount of time to complete tasks in the queue. The roadside assistance service provider system 600 may also consider and factor the skill levels required to complete a given task, for example a skill level 1 may use a factor of 2 for time estimates. The roadside assistance service provider system 600 may also consider and factor the skill level and whether a driver or roadside assistance service provider is allowed and/or capable of working on a specific job or task, utilizing it as a qualifier. The roadside assistance service provider system 600 may also consider and factor the price of the driver, any particular skills of the driver, the match with the user or customer, and the equipment of the driver. The roadside assistance service provider system 600 may also consider how long the driver will take at their current job, utilizing information from the collection module 610. The roadside assistance service provider system 600 may also consider weather, time of day, traffic, neighborhood, type of road, etc. which may cause the tasks onsite to take longer to perform. The roadside assistance service provider system 600 may also utilize driver performance as a factor in assignment of the next jobs and prioritize tasks at which a certain driver is strong. Other factors and/or considerations may be utilized for assigning roadside assistance service providers without departing from this invention.

Additionally, in this step 815, the telematics information of the roadside assistance service providers and the user may be sent from a telematics device 225 located in the vehicle or as part of the mobile device 215. The telematics information may include information regarding the user and/or the customer's distressed vehicle. The telematics information may also include information regarding the roadside assistance service provider and/or the roadside assistance service provider's vehicle. The telematics information may include information such as location, velocity (both instantaneous and/or average), direction of travel, route and final destination. This telematics information may then be utilized to assist in providing further information to the roadside assistance service provider system 600. Utilizing telematics information and/or insurance information (driving habits), the roadside assistance service provider system 600 may know the driving routes and the known locations of various roadside assistance service providers when the service request is made and may therefore match up given roadside assistance service providers who are located advantageously to the location that the roadside assistance services will be performed.

In step 820, the roadside assistance service provider system 600 may rank the roadside assistance service providers. The rankings may be based on time, then by distance if there is a tie, and then by on time performance if there is still a tie. The rankings may also be based on any of the factors utilized during step 715. Other rankings may be utilized for the roadside assistance service providers without departing from this invention.

Following the rankings, in step 825, the roadside assistance service provider system 600 may then send invitations and or assignments to the drivers or the roadside assistance service provider. If the driver accepts the invitation and assignment, the roadside assistance service provider system 600 may assign the roadside assistance service request to the driver. If the driver does not accept the invitation and assignment, the roadside assistance service provider system 600 may send the roadside assistance service request to the next driver or roadside assistance service provider on the list. Additionally, if there is no assignment after a given time frame (for example 10 minutes), then the roadside assistance service provider system 600 may send the roadside assistance service request back to a manual dispatcher for manual assignment.

In step 830, the roadside assistance service provider system 600 provides reassignment adjustments. In this step 830, roadside assistance service provider system 600 may shuffle the assignments during the middle of the assignment process. The roadside assistance service provider system 600 may shuffle current workloads as long as the driver or roadside assistance service provider is not yet at the roadside assistance site. Various situations may trigger the reassignment. The roadside assistance service provider system 600 may trigger a reassignment such as flagging of a roadside assistance service request as a priority roadside assistance service in which particular jobs may override other jobs and may be highlighted to dynamically reassign jobs. One example of this priority flagging reassignment may be a person stranded on a highway and needs attention immediately. Another example of this priority flagging reassignment may be a person or distressed vehicle stranded in a dangerous location and needing attention immediately. Another situation that may trigger a reassignment may be the shifting of work to other roadside assistance service providers in a particular roadside assistance service provider is moving slowly during a given day. In this instance, the roadside assistance service provider system 600 provides a centralized screen or output to show how different roadside assistance service providers are working and performing.

In step 835, the roadside assistance service provider system 600 provides roadside assistance event notifications for the roadside assistance services provided. In step 835, the roadside assistance service provider system 600 may display and or provide feedback for various events and tasks during the roadside assistance services. In this step 835, the roadside assistance service provider system 600 may provide various service notifications from the service provider to the user. The roadside assistance service provider system 600 may provide the user with information regarding the status of the services, i.e. service confirmation, start time, service provider en-route, service provider onsite, service completed, and/or service canceled. Furthermore, in step 835, the roadside assistance service provider system 600, the feedback and display may provide near real-time cues to the tow truck driver's mobile device, such as alerting when the amount of time spent on a task exceeds a predefined threshold, flagging high priority tasks/assignments, providing a step-by-step checklist for the repair, etc., performance measurements, and award points/score to the tow truck driver.

In step 840, the roadside assistance service provider system 600 provides rewards based on the roadside assistance service provided. In this step 840, the roadside assistance service provider system 600 may be configured to provide a reward to an individual driver or roadside assistance service provider or roadside assistance service provider company if particular times are met. For example, the reward may allow a driver to move up in a queue in a definitive way if the roadside assistance service provider beats the estimate time or suggested times. Additionally, the roadside assistance service provider system 600 may provide an individual driver or roadside assistance service provider an additional award if the job or tasks are done more quickly. The roadside assistance service provider system 600 may provide awards based on accurate estimates and not necessarily doing a job or task more quickly.

In step 845, the roadside assistance service provider system 600 provides performance feedback for the roadside assistance service provider. In this step 845, the roadside assistance service provider system 600 may also include a performance output or screen, which displays to the driver whether the driver is within their estimated time of arrival for meeting their roadside assistance service request. The roadside assistance service provider system 600 may also display or output to the driver whether the driver's performance meets average performance as well as the driver's past performance for the given tasks or roadside assistance services. The roadside assistance service provider system 600 may also calculate a performance score based on the given tasks or roadside assistance services. The roadside assistance service provider system 600 may output or display the driver's performance score that depends on the driver's ability to meet the timing of tasks as estimated or required. The roadside assistance service provider system 600 may also be able to identify a driver that performs weak at certain tasks for training the driver in those given tasks.

According to some arrangements, the process described with respect to FIG. 8 may be provided by a roadside assistance service provider system 600, a mobile service provider application 602, or a service provider application executing on a device such as a service provider's mobile communication device 215 or service provider server 605, through the internet or on a webpage, or a service provider's vehicle computer or navigation system.

The processes, systems and other features described herein may be applied to all types of services. For example, similar features and systems may be used to provide applications corresponding to automobile services, road services, home services, and personal services.

While the invention has been described with respect to specific examples and includes presently preferred modes of carrying out the invention, those skilled in the art will appreciate that there are numerous variations and permutations of the above described systems and techniques that fall within the spirit and scope of this disclosure. 

We claim:
 1. A roadside assistance system, the system comprising: a roadside assistance service provider server having at least one processor; a roadside assistance service provider application for use on a mobile device and executing on the roadside assistance service provider server; a plurality of sensors positioned on a vehicle of a roadside assistance service provider, wherein the plurality of sensors collects roadside assistance service provider information, wherein the roadside assistance service provider is a selected service provider from a group of individuals who are non-professional service providers; and a telematics device in communication with a distressed vehicle and in communication with the roadside assistance service provider application, wherein the telematics device provides telematics information to the roadside assistance service provider application and the roadside assistance service provider server; wherein the roadside assistance service provider application upon execution of computer-executable instructions from the roadside assistance service provider server is configured to: receive, by the roadside assistance service provider server, a roadside assistance service request from a driver of the distressed vehicle, wherein the roadside assistance service request includes one or more of the following: jump start the distressed vehicle, flat tire change, fuel a lack of fuel vehicle, or unlock a locked out vehicle; determine, by the roadside assistance service provider server, the selected service provider based on a proximity in location between the distressed vehicle and the selected service provider; send, by the roadside assistance service provider server to the roadside assistance service provider application, the roadside assistance service request to the selected service provider; receive, through the roadside assistance service provider application, acceptance of the roadside assistance service request from the selected service provider; provide, by the roadside assistance service provider server and the telematics device and plurality of sensors, event notifications to the roadside assistance service provider application of a status of the selected service provider with respect to the roadside assistance service request, wherein the event notifications are near real-time cues to the roadside assistance service provider via the mobile device; and receive, through the roadside assistance service provider application, confirmation of completion of the roadside assistance service request from the selected service provider.
 2. The roadside assistance system of claim 1, wherein the event notifications include one or more of the following: time until arrival, alerting when an amount of time spent on a task exceeds a predefined threshold, flagging high priority tasks, flagging high priority assignments, and providing a step-by-step checklist for the roadside assistance service request.
 3. The roadside assistance system of claim 1, wherein the telematics information includes location, velocity, route, and destination.
 4. The roadside assistance system of claim 1, wherein the roadside assistance service provider information includes a location of the selected service provider, a type of the selected service provider, a set of ratings of the selected service provider.
 5. The roadside assistance system of claim 1, wherein the roadside assistance service provider information includes real-time information that includes one or more of the following: an availability of the selected service provider, a start time for the selected service provider, or a completion time for the selected service provider.
 6. The roadside assistance system of claim 1, wherein the event notification is provided on a display through the roadside assistance service provider application to the selected service provider.
 7. The roadside assistance system of claim 1, wherein the roadside assistance service provider application upon execution of computer-executable instructions from the roadside assistance service provider server is further configured to: provide, by the roadside assistance service provider server and through the roadside assistance service provider application, electronic payment for completing the roadside assistance service request to the selected service provider.
 8. The roadside assistance system of claim 7, wherein the electronic payment is automatic with a pre-entered payment method when the roadside assistance service request is complete.
 9. The roadside assistance system of claim 1, wherein the roadside assistance service provider application upon execution of computer-executable instructions from the roadside assistance service provider server is further configured to: receive, by the roadside assistance service provider server, an evaluation from a driver of the distressed vehicle of the selected service provider after the roadside assistance service request is complete.
 10. The roadside assistance system of claim 1, wherein the roadside assistance service provider application upon execution of computer-executable instructions from the roadside assistance service provider server is further configured to: receive, by the roadside assistance service provider server, an evaluation from the selected service provider of the driver of the distressed vehicle after the roadside assistance service request is complete.
 11. The roadside assistance system of claim 1, wherein the roadside assistance service provider application upon execution of computer-executable instructions from the roadside assistance service provider server is further configured to: receive, by the roadside assistance service provider server, a registration from the group of individuals who are non-professional service providers, wherein the registration includes interviews, background checks, and a driver's record check.
 12. The roadside assistance system of claim 11, wherein the registration further includes validation of completed training for the group of individuals who are non-professional service providers.
 13. One or more non-transitory computer readable media storing computer readable instructions that, when executed, cause an apparatus to: (a) receive, through a roadside assistance service provider application for use on a mobile device executing on a roadside assistance service provider server having at least one processor, a roadside assistance service request from a driver of a distressed vehicle; (b) collect roadside assistance service provider information by a plurality of sensors in communication with a vehicle of a roadside assistance service provider, wherein the roadside assistance service provider is a selected service provider from a group of individuals who are non-professional service providers; (c) receive, by the roadside assistance service provider server, telematics information from a telematics device wirelessly connected to the distressed vehicle; (d) receive, by the roadside assistance service provider server, a roadside assistance service request from the driver of the distressed vehicle, wherein the roadside assistance service request includes one or more of the following: jump start the distressed vehicle, flat tire change, fuel a lack of fuel vehicle, or unlock a locked out vehicle; (e) determine, by the roadside assistance service provider server, the selected service provider based on one or more factors, wherein the one or more factors include one or more of the following: proximity in location between the distressed vehicle and the selected service provider, prior driver's ratings for the selected service provider, a skill set of the selected service provider, or a cost of the selected service provider; (f) send, by the roadside assistance service provider server to the roadside assistance service provider application, the roadside assistance service request to the selected service provider; (g) receive, through the roadside assistance service provider application, acceptance of the roadside assistance service request from the selected service provider; (h) provide, by the roadside assistance service provider server and the telematics device and plurality of sensors, event notifications to the roadside assistance service provider application of a status of the selected service provider with respect to the roadside assistance service request; and (i) receive, through the roadside assistance service provider application, confirmation of completion of the roadside assistance service request from the selected service provider.
 14. The one or more non-transitory computer readable media storing computer readable instructions of claim 13, wherein the telematics information includes location, velocity, route, and destination.
 15. The one or more non-transitory computer readable media storing computer readable instructions of claim 13, wherein the roadside assistance service provider information includes real-time information that includes one or more of the following: an availability of the selected service provider, a start time for the selected service provider, or a completion time for the selected service provider.
 16. The one or more non-transitory computer readable media storing computer readable instructions of claim 13 that, when executed, cause an apparatus to further: provide, by the roadside assistance service provider server and through the roadside assistance service provider application, electronic payment for completing the roadside assistance service request to the selected service provider, wherein the electronic payment is automatic with a pre-entered payment method when the roadside assistance service request is complete.
 17. The one or more non-transitory computer readable media storing computer readable instructions of claim 13 that, when executed, cause an apparatus to further: receive, by the roadside assistance service provider server, a registration from the group of individuals who are non-professional service providers, wherein the registration includes interviews, background checks, and a driver's record check, wherein the registration further includes validation of completed training for the group of individuals who are non-professional service providers.
 18. A roadside assistance system, the system comprising: a roadside assistance service provider server having at least one processor; a roadside assistance service provider application for use on a mobile device and executing on the roadside assistance service provider server; a plurality of sensors positioned on a vehicle of a roadside assistance service provider, wherein the plurality of sensors collects roadside assistance service provider information, wherein the roadside assistance service provider is a selected service provider from a group of individuals who are non-professional service providers; and a telematics device in communication with a distressed vehicle and in communication with the roadside assistance service provider application, wherein the telematics device provides telematics information to the roadside assistance service provider application and the roadside assistance service provider server; wherein the roadside assistance service provider application upon execution of computer-executable instructions from the roadside assistance service provider server is configured to: receive, by the roadside assistance service provider server, a registration from the group of individuals who are non-professional service providers, wherein the registration includes interviews, background checks, and a driver's record check, wherein the registration further includes validation of completed training for the group of individuals who are non-professional service providers; receive, by the roadside assistance service provider server, a roadside assistance service request from the driver of the distressed vehicle, wherein the roadside assistance service request includes one or more of the following: jump start the distressed vehicle, flat tire change, fuel a lack of fuel vehicle, or unlock a locked out vehicle; determine, by the roadside assistance service provider server, the selected service provider based on one or more factors, wherein the one or more factors include one or more of the following: proximity in location between the distressed vehicle and the selected service provider, prior driver's ratings for the selected service provider, a skill set of the selected service provider, or a cost of the selected service provider; send, by the roadside assistance service provider server to the roadside assistance service provider application, the roadside assistance service request to the selected service provider; receive, through the roadside assistance service provider application, acceptance of the roadside assistance service request from the selected service provider; and receive, through the roadside assistance service provider application, confirmation of completion of the roadside assistance service request from the selected service provider.
 19. The roadside assistance system of claim 18, wherein the roadside assistance service provider information includes real-time information that includes one or more of the following: an availability of the selected service provider, a start time for the selected service provider, or a completion time for the selected service provider.
 20. The roadside assistance system of claim 18, wherein the roadside assistance service provider application upon execution of computer-executable instructions from the roadside assistance service provider server is further configured to: provide, by the roadside assistance service provider server and through the roadside assistance service provider application, electronic payment for completing the roadside assistance service request to the selected service provider, wherein the electronic payment is automatic with a pre-entered payment method when the roadside assistance service request is complete. 